home account info subscribe login search FAQ/help site map contact us


 
Brief Full
 Advanced
      Search
 Search Tips
To access the contents, click the chapter and section titles.

Bug Proofing Visual Basic: A Guide to Error Handling and Prevention
(Publisher: John Wiley & Sons, Inc.)
Author(s): Rod Stephens
ISBN: 0471323519
Publication Date: 11/01/98

Search this book:
 
Previous Table of Contents Next


Summary

Testing may not be much fun, but it is certainly better than endless bug chasing. Test properly and often to catch bugs as quickly as possible. In the long run, testing will let you spend less time in pursuit of bugs and more time doing more interesting things, such as coding. The following Bug Stoppers summarize the testing concepts described in this chapter.

BUG STOPPERS: testing
Use lots of different kinds of tests.
Test using different techniques.
Test at routine, module, subsystem, and system levels.
Test during all phases of development.
After you finish a routine, step through it using the debugger.
Hold code reviews.
Test exhaustively if possible.
Use black box testing.
Use white box testing.
Don’t forget, global variables are inputs, too.
Plan tests ahead of time.
Test continuously throughout the project.
Test right away.
Have the attitude that testing is intended to catch bugs.
Write test routines and save them for later.
Look for bugs. Don’t just check tests off a list.
Test when you are alert.
Retest code any time you make changes.
Test when you port code.
Start routines from the Immediate window.
Examine variables using quick watches and the Immediate window.
Modify variables using the Immediate window.
Use Ctrl-F9 to jump to other parts of the code.
Examine decision statements carefully.
Know what outputs to expect before you perform a test.
Simulate errors.
Find your own bugs.
Have someone else test your code, too.
Don’t shoot the messenger. Testers do not cause bugs, they only find them.
Fix your own code.
Simulate user actions to automate testing.
Check code coverage and examine unused code.
Keep testing until you cannot find any more bugs.
Estimate the number of bugs.
Estimate bug finding time.
Test user interfaces from the top down.
Test complex code from the bottom up.
Perform a postmortem to learn from your mistakes.


Previous Table of Contents Next


Products |  Contact Us |  About Us |  Privacy  |  Ad Info  |  Home

Use of this site is subject to certain Terms & Conditions, Copyright © 1996-1999 EarthWeb Inc.
All rights reserved. Reproduction whole or in part in any form or medium without express written permision of EarthWeb is prohibited.